1 results listed
Keeping the quality goals in software is not a matter of chance. It needs proper planning and continuous attention of the development team. The main responsible for achieving the quality goals is the software architect. The architect needs to contribute in: clarifying and defining the goals, make a design that maps the required quality. However, that’s not enough. The architect needs to govern all development and test activities to move towards the goals in harmony as a team. In the end, software quality depends on the design decisions, implementation and the also definition of the goals itself. A process for tracking the architectural quality is presented in this paper with an analogy to the development processes: “V Model” and “W Model”.
International Conference on Advanced Technologies, Computer Engineering and Science
ICATCES
Onur Taviloglu
Fatih Cetin